I build embedded products end‑to‑end, from first prototype to production.

Full-stack embedded engineer. I own the whole path — MCU firmware, multi-board and dual-core architecture, the embedded Linux host layer, secure OTA, and the production test tooling that gets a device out the factory door. Not just one layer of the stack.

“Two processors in one product disagree about what’s true.”

“Every board variant needs its own firmware, and now you maintain five codebases.”

“An OTA update can brick a unit in a customer’s home.”

Pressure-mat prototype to a shipping product on the CES 2026 floor — five boards, one platform.

Unclear requirements are the normal starting condition, so I don’t wait for a spec — I write down the three numbers the product actually has to hit and get you to disagree with them. Before I write firmware I want the hardware in my hands, a schematic, and one measurable definition of done; if a number can’t be measured on a bench, I’ll tell you so rather than quietly hope. You get a written note every Friday: what moved, what I measured, what I got wrong, and what I need from you next week. When I think the plan is wrong I say it early, in writing, with the alternative attached.

Review & audit

I read the firmware, the schematic and the failure reports, then tell you where this design will break — timing, state ownership, update safety, production testability — and what I would change first.

Scope

Code and architecture review, ranked findings, written recommendation

Duration

1–2 weeks

Rate

On request

Architecture

I design the system and write the decisions down — where state lives, what each board owns, transport and framing, update and recovery behaviour — so your team can build it without guessing.

Scope

Architecture document, interface contracts, decision record, review sessions

Duration

4–8 weeks

Rate

On request

Execution

Defined firmware work against an architecture that already exists: board bring-up, drivers written from the datasheet, one subsystem, the secure update path, or the production test tool.

Scope

Bring-up, drivers, one subsystem or the OTA path, delivered with tests

Duration

3–8 weeks

Rate

On request

Start with a call. Bring the block diagram, or the argument you’re having about it.

30 minutes. I’ll tell you whether the timing budget is realistic, where I think the state should live, and what I’d architect differently — whether or not you hire me.

Send the shape of the system and the constraint that worries you. Five fields, no funnel.